Systems and media for managing electronic asset tags for asset devices

ABSTRACT

Systems, methods, and media for managing electronic asset tags for asset devices are disclosed. Embodiments include a system having one or more asset devices in communication with a network where each asset device has an electronic asset tag, where the electronic asset tag has contents including an asset number associated with the asset device having the electronic asset tag. The system may also include an asset tag manager in communication with the network to access the contents of the electronic asset tags of the one or more asset devices. In a further embodiment, the asset tag manager may be adapted to modify the contents of the electronic asset tags of the one or more asset devices. In another further embodiment, the asset tag manager may be adapted to reload to an asset device the contents of the electronic asset tag of the asset device.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of application Ser. No. 11/134,922filed on May 23, 2005, which is incorporated herein by reference in itsentirety.

FIELD OF INVENTION

The present invention generally relates to the field of computersystems. More particularly, the present invention relates to systems,methods, and media for managing electronic asset tags for asset devices.

BACKGROUND

Outsourcing is a major trend in the Information Technology (IT)industry. In some outsourced engagements, the outsourcer deploysoutsourcer-owned devices at different geographical locations of thecustomer. A customer may outsource its printing services, for example,by engaging an outsourcer to deploy its printers at the customer'sfacilities. The outsourcer in this arrangement will typically own theprinters and be responsible for their maintenance. The outsourcer willthen typically charge the customer a flat rate and/or a cost per printedpage. Such an outsourcing arrangement benefits customers by providinguse of the equipment without having to purchase expensive capital assetsor having to maintain such assets, while the outsourcer benefits byhaving a relatively stable source of income from its outsourcingservices. Outsourcing arrangements are likely to increase as more andmore companies or other organizations desire to reduce their investmentin capital equipment or other assets.

Organizations track assets in order to provide records for depreciationor other financial record needs. In order to track their assets,outsourcing organizations typically assign asset numbers to particularpieces of equipment to facilitate tracking and audits by theoutsourcer's business control organization. The asset number is oftenindependent from the serial number for the equipment and is instead usedfor internal controls. One common solution to implement asset numbersfor a large group of assets is to use physical asset tags. In thisimplementation, the asset number is printed on a sticker or label andattached directly to the asset. This allows outsourcer personnel to walkup to the asset and quickly read the asset number from the asset tag.

Physical asset tags, however, are plagued by a number of problems.First, physical asset tags must be physically applied to the assets,requiring significant costs in labor and time. Outsourcers often, forexample, physically apply the asset tag at a consolidation center priorto delivery to a customer or at the customer facility itself. Applyingthe asset tag at a consolidation center results in additional incurredcosts and delays for transportation to the consolidation center as wellas the costs of unpacking and repacking the asset in order to attach theasset tag. Physical asset tags also require auditors from theoutsourcing organization's business controls group to physically viewthe assets at the customer facility, requiring the costs and delays oftransportation to the customer facilities (which may be worldwide) aswell as a possible distraction or inconvenience for the customer.Another potential problem with physical asset tags is that errors whichresult in a mismatch of the physical asset tag and the devicemanufacturer's serial number require manual labor to reconcile. Sucherrors occur when the serial number changes as hardware is replaced forrepair, resulting in the mismatch of the physical asset tag and serialnumber. Yet another problem is the possibility of a transcription errorwhen an auditor or other person records the value of an asset number.

Another solution for outsourcers is to utilize Radio FrequencyIdentification (RFID) asset tags. RFID asset tags contain a smalltransponder that remains in a sleep state until activated by a signalfrom an activator, after which the RFID asset tag emits a radio signalcontaining the asset number of the device with the RFID asset tag. Theactivator receives the radio signal and asset number and then forwardsthe information to another computer system. An employee of theoutsourcer may thus walk around a customer facility to gather RFID assettag information, eliminating the need to transcribe a physical asset tagand saving time. RFID asset tags, while powerful, retain thedisadvantages of the physical asset tags, as they require physicalattachment to the asset device and require an auditor to be in physicalproximity to the asset device in order to receive the RFID asset tagtransmission.

There is, therefore, a need for an effective and efficient system tomanage asset devices. There is an even greater need for such a systemwhen the asset devices are geographically distributed over a large area.

SUMMARY OF THE INVENTION

The problems identified above are in large part addressed by systems,methods, and media for managing electronic asset tags of asset devices.One embodiment generally provides a method for accessing an electronicasset tag of an asset device, the electronic asset tag having contentscomprising an asset number. The method may also generally includeproviding electronic asset tag authorization to the asset device and,after providing the electronic asset tag authorization, modifying thecontents of the electronic asset tag of the asset device. Furtherembodiments may include initializing a network connection with the assetdevice or, after modifying the electronic asset tag, recording anindication of a status for the electronic asset tag. A furtherembodiment may include recording the contents of the electronic assettag to a backup device and reloading the contents of the electronicasset tag from the backup device to the electronic asset tag of theasset device.

Another embodiment provides a machine-accessible medium containinginstructions effective, when executing in a data processing system, tocause the system to perform a series of operations for synchronizing adatabase on a network. The series of operations generally includesaccessing an electronic asset tag of an asset device, the electronicasset tag having contents comprising an asset number. The series ofoperations may also generally include providing electronic asset tagauthorization to the asset device and, after providing the electronicasset tag authorization, modifying the contents of the electronic assettag of the asset device. Further embodiments may include initializing anetwork connection with the asset device or, after modifying theelectronic asset tag, recording an indication of a status for theelectronic asset tag. A further embodiment may include recording thecontents of the electronic asset tag to a backup device and reloadingthe contents of the electronic asset tag from the backup device to theelectronic asset tag of the asset device.

A further embodiment provides a system for managing asset numbers. Thesystem may include one or more asset devices in communication with anetwork where each asset device having an electronic asset tag, wherethe electronic asset tag has contents including an asset numberassociated with the asset device having the electronic asset tag. Thesystem may also include an asset tag manager in communication with thenetwork to access the contents of the electronic asset tags of the oneor more asset devices. In a further embodiment, the asset tag managermay be adapted to modify the contents of the electronic asset tags ofthe one or more asset devices. In another further embodiment, the assettag manager may be adapted to reload to an asset device the contents ofthe electronic asset tag of the asset device.

BRIEF DESCRIPTION OF THE DRAWINGS

Other objects and advantages of the invention will become apparent uponreading the following detailed description and upon reference to theaccompanying drawings in which, like references may indicate similarelements:

FIG. 1 depicts an environment for managing electronic asset tags for oneor more asset devices according to one embodiment;

FIG. 2 depicts an example of a flow chart for remotely modifying theelectronic asset tag of an asset device according to one embodiment;

FIG. 3 depicts an example of a flow chart for manually modifying theelectronic asset tag of an asset device according to one embodiment;

FIG. 4 depicts an example of a flow chart for modifying the electronicasset tag of an asset device in response to an authorized requestaccording to one embodiment; and

FIG. 5 depicts an example of a flow chart for backing up and restoringthe electronic asset tag of an asset device according to one embodiment.

DETAILED DESCRIPTION OF EMBODIMENTS

The following is a detailed description of example embodiments of theinvention depicted in the accompanying drawings. The example embodimentsare in such detail as to clearly communicate the invention. However, theamount of detail offered is not intended to limit the anticipatedvariations of embodiments; but, on the contrary, the intention is tocover all modifications, equivalents, and alternatives falling withinthe spirit and scope of the present invention as defined by the appendedclaims. The detailed descriptions below are designed to make suchembodiments obvious to a person of ordinary skill in the art.

Methods, systems, and media for managing electronic asset tags for assetdevices are disclosed. Embodiments include a system having one or moreasset devices in communication with a network where each asset devicehas an electronic asset tag, where the electronic asset tag has contentsincluding an asset number associated with the asset device having theelectronic asset tag. The system may also include an asset tag managerin communication with the network to access the contents of theelectronic asset tags of the one or more asset devices. In a furtherembodiment, the asset tag manager may be adapted to modify the contentsof the electronic asset tags of the one or more asset devices. Inanother further embodiment, the asset tag manager may be adapted toreload to an asset device the contents of the electronic asset tag ofthe asset device.

The systems, methods, and media of the disclosed embodiments provide animproved methodology for managing and tracking asset devices. Theelectronic asset tag provides a relatively permanent and efficientmethod for managing individual asset devices which may be geographicallyspread across the world. The asset tag manager allows for a centralizedrepository of asset number information which may be updated andmaintained without requiring individuals to physically visit the assetdevices, potentially saving large amounts of time and money fororganizations with distributed assets. Electronic asset tags may alsoreduce or eliminate transcription errors as well as reducing the numberof mismatches between asset tags and device serial numbers. Electronicasset tags, which may include the asset number, may be restored in theevent of device failure from either the central asset tag manager or alocal external device, providing an additional layer of permanence tothe asset number. Organizations desiring to track assets fordepreciation or other purposes may use the disclosed system to assist intracking and managing their assets, saving a significant amount ofresources when assets are widely distributed.

Turning now to the drawings, FIG. 1 depicts an environment for managingelectronic asset tags for one or more asset devices according to oneembodiment. Asset management system 100 may include an asset tag manager102 in communication with one or more asset devices 106 via a network104. Each asset device 106 may contain an electronic asset tag 108 whichitself contains an asset number associated with the asset devices 106.The asset management system 100 may facilitate tracking and updating ofasset numbers (and electronic asset tags 108 that contain them) by theasset tag manager 102 for each of the asset devices 106. In addition tothe capabilities of the asset tag manager 102, an authorized person inthe same physical location as an asset device 106 may also access and/orupdate the asset number.

The components of the asset management system 100 may be located at thesame location, such as in the same building or computer lab, or could beremote. While the term “remote” is used with reference to the distancebetween the components of the asset management system 100, the term isused in the sense of indicating separation of some sort, rather than inthe sense of indicating a large physical distance between the systems.In one example, the asset tag manager 102 may be located at a centrallocation of an outsourcer while a plurality of asset devices 106 aredistributed across a customer's facilities worldwide.

Network 104 may be any type of data communications channel, such as theInternet, an intranet, a LAN, a WAN, an Ethernet network, or a wirelessnetwork. Those skilled in the art will recognize that any type of datacommunication channel between the asset tag manager 102 and the assetdevices 106 may be used without departure from the scope and spirit ofthe invention.

The asset tag manager 102 may, in one embodiment, be software and/orstate machines implemented on one or more of any type of computersystem, including servers, personal computers, workstations, mainframecomputers, notebook or laptop computers, desktop computers, or the like.In one example, the asset tag manager 102 or any of its components maybe implemented on an IBM® eServer or similar server having one or moreprocessors, or threads of processors, executing software and/or one ormore state machines coupled with data storage devices such as randomaccess memory (RAM), read only memory (ROM), flash memory, compact diskdrives, hard drives, and the like. In one embodiment, the asset tagmanager 102 may include an e-asset tag manager 114 and an e-asset tagmonitor 116. The asset tag manager 102 may also be in communication withor include a database 112 for storage of asset tags or any otherinformation.

The e-asset tag manager 114 may remotely and electronically set theasset number for any of the asset devices 106. In one embodiment, a userof the asset tag manager 102 may use the e-asset tag manager 114 toremotely set the asset number of the electronic asset tag 108 for one ormore asset devices 106 without having to be in physical proximity to theasset device 106. The user, through the e-asset tag manager 114, mayoptionally provide authorization to the electronic asset tag 108 beforebeing permitted to set or otherwise modify the asset number of theelectronic asset tag 108. Requiring authorization helps ensure integrityof the information stored in the electronic asset tag 108 as only usershaving the proper authorization will be permitted to modify or set thecontents of the electronic asset tag 108. Authorization may be performedin any manner, such as by requiring one or more of a proper password,digital signatures, digital authentication, computer systemidentification, or the like. The e-asset tag manager 114 may alsorequire authorization for read operations in addition to modifyoperations to help avoid issues such as “spoofing”.

The e-asset tag monitor 116 may remotely monitor the contents of theelectronic asset tags 108 of a plurality of distributed asset devices106. An auditor or other user, for example, may view the contents of anyelectronic asset tags 108 without having to leave their currentlocation. In one embodiment, the e-asset tag monitor 116 may access theelectronic asset tags 108 automatically to ascertain the status of theasset devices 106. In another embodiment, the e-asset tag monitor 116may access the electronic asset tags 108 upon user request or upon auser-defined schedule. The e-asset tag monitor 116 may use anymethodology to access the information within the electronic asset tags108. The e-asset tag monitor 116 may also store content from theelectronic asset tags 108 in database 112 for later retrieval or access.

The one or more asset devices 106 may be any physical assets for whichasset numbers are used. Asset devices 106 may include printers (such aslarge system printers), computer systems or components, industrialdevices, robotic devices, or any other device. In one embodiment, eachasset device 106 may be connected with network 104, allowing the assetdevice 106 to communicate with the asset tag manager 102. In oneexample, the asset device 106 may use the Simple Network ManagementProtocol (SNMP) or other protocol to facilitate communication with theasset tag manager 102. The SNMP is an application layer protocol that ispart of the Transmission Control Protocol/Internet Protocol (TCP/IP)suite and is designed to facilitate the exchange of information betweennetworked devices. The asset devices 106 may serve as managed devices ofthe SNMP network having an SNMP agent while the asset tag manager 102may serve as the SNMP network management system (NMS). In anotherexample, network 104 may include a local network using a protocol suchas SNMP and a cross site network using a protocol such as Web Serviceswith a gateway server between the two parts of the network 104. Thelocal network of this example may be characterized by higher transactionrates and lower security requirements while the external cross sitenetwork may be characterized by lower transaction rates and highersecurity requirements. In this example, the asset tag manager 102 mayserve as the gateway server. One skilled in the art will recognize thatother network or communications protocols may also be used.

The electronic asset tag 108 may include an asset number or any othertype of information. The electronic asset tag 108 may include, in oneexample, information about the outsourcer (or other operator of theasset tag manager 102) or the customer (or other operator of the assetdevice 106). Any other type of information may be stored in theelectronic asset tag 108, such as maintenance, upgrade information, orasset device 106 history. Asset numbers may be any type of number orother identifier that is associated with a particular asset. Assetnumbers may be different than serial numbers, as serial numbers aretypically associated with particular pieces of hardware. In somesituations, an asset with a fixed asset number may have changes to itshardware that result in changes to serial numbers. Accordingly, assetnumbers may advantageously be more permanent than serial numbers and arethus more suitable for financial purposes such as managing assetdepreciation.

The electronic asset tag 108 may be located anywhere within or as partof a particular asset device 106. In one embodiment, the electronicasset tag 108 may be included in nonvolatile device memory of the assetdevice 106 so that the contents of the electronic asset tag 108 arepersistent in the event of power interruption. The electronic asset tag108 may be stored in an existing memory of the asset device 106, such asby storing it in a network protocol accessible field, so that the assetdevice 106 need not be sent to a consolidation facility for inclusion ofthe electronic asset tag 108. Alternatively, the electronic asset tag108 may be stored in a separate or dedicated memory component.

In a further embodiment, the electronic asset tag 108 may be stored intwo or more locations in the asset device 106. Storing the electronicasset tag 108 in multiple locations provides additional security of theelectronic asset tag 108 by preventing a single component failure fromerasing the contents of the electronic asset tag 108. If an asset device106 stores the electronic asset tag 108 in non-volatile memory of aprocessor as well as on a hard drive, the failure of one of thosecomponents will not result in the loss of the electronic asset tag 108contents. If the hard drive crashed and was replaced in this example,one of its first tasks could be to gather the contents of the electronicasset tag 108 from the processor and to save those contents in itsmemory, reestablishing the redundant storage of the electronic assettag.

In another further embodiment, the contents of the electronic asset tag108 may be downloaded to a separate backup device 110. A user with theappropriate permissions may use the backup device 110 to restore thecontents of the electronic asset tag 108 in the event of a replacedhardware part, data loss, or other event. The backup device 110 may beany type of storage device, such as a disk, USB or flash memory or card,or the like. In another embodiment, the backup device 108 may be anetwork drive or other backup device accessed over network 104.

The system of the disclosed embodiments provides an effective andefficient methodology for managing asset numbers of a plurality ofdistributed asset devices 106. Asset numbers and other information maybe located in an electronic asset tag 108 of each network-connectedasset device 106. A user may use the asset tag manager 102 to manage theasset numbers of the asset devices 106 by setting and accessing theelectronic asset tags 108 of the remote asset devices 106 without havingto be in the physical proximity of the asset devices 106. A user maytherefore advantageously remotely set, update, and access the assetnumbers stored in the electronic asset tags 108 of distributed assetdevices 106. The system of the disclosed embodiments may also providepermanence to asset numbers stored in electronic asset tags 108 bystoring them in a central location, in multiple locations in the assetdevice 106, and/or on a backup device 110. The disclosed system may alsohelp prevent transcription errors and mismatches between device serialnumbers and asset numbers. Organizations may use the disclosed systemfor managing the depreciation of assets or for other financial tasks, asthe disclosed system may advantageously provide an efficient method oftracking assets with asset numbers that do not suffer from the possibleuncertainty of serial numbers.

The system of the disclosed embodiments may be used in an outsourcedprinting services situation in one exemplary example. In this example, aprinting services outsourcer may operate an asset tag manager 102 tomanage a plurality of asset devices 106 such as system printers. Thesystem printers may be distributed at customer facilitiesgeographically-distributed around the world. The outsourcer may thusmanage the asset devices 106 from a central location without having tovisit each customer facility to audit or otherwise access the systemprinters, saving valuable resources. If the existing hardware and/orsoftware of the asset device 106 is used to store the contents of theelectronic asset tag 108, the need to send asset devices 106 to aconsolidation facility is also eliminated, saving additional time andmoney. While the example described above relates to outsourced printingservices, one skilled in the art will recognize that the disclosedsystem is suitable for any type of asset devices 106, and isparticularly suitable for distributed, networked devices. In anotherexample, the disclosed system may be used in a non-outsourcing situationfor an organization with a large number of distributed assets that arevaluable and network attached, such as laptop computer systems in alarge corporate facility.

FIG. 2 depicts an example of a flow chart for remotely modifying theelectronic asset tag of an asset device according to one embodiment. Theelements of flow chart 200 may be performed, in one embodiment, bycomponents or combinations of components of the asset tag manager 102.Flow chart 200 begins with element 202, initializing a connection withan asset device 106. In one embodiment, the asset tag manager 102 mayperform element 202 by establishing a network connection over network104 with an asset device 106, such as an SNMP connection. Afterinitializing the connection with the asset device 106, the asset tagmanager 102 may access the contents of the electronic asset tag 108 atelement 204. A user of the asset tag manager 102 may, for example,access the asset number associated with an asset device 106 formonitoring or tracking purposes. The user may typically access any ofthe contents of the electronic asset tag 108 without providing apassword or other authentication.

The method of flow chart 200 continues to decision block 206, where theasset tag manager 102 determines whether it should set or otherwisemodify the contents of the electronic asset tag 108. In one embodiment,a user of the asset tag manager 102 may request modification of theelectronic asset tag 108, such as when asset numbers are being assignedor customer information need be modified. In another embodiment, theasset tag manager 102 may automatically determine a need to modify theelectronic asset tag 108, such as in response to a particular event orschedule. If the asset tag manager 102 will attempt to modify thecontents of the electronic asset tag 108, flow chart 200 continues toelement 208; otherwise, flow chart 200 continues to element 214.

At element 208, the asset tag manager 102 provides electronic asset tagauthorization to the electronic asset tag 108 and/or asset device 106.The asset tag manager 102 may provide authorization in any fashion, suchas a password, computer system identification, digital signature,digital authentication, or the like. The asset tag manager 102 mayreceive information related to the authorization (e.g., a password) froma user or such information may be stored. The asset tag manager 102determines at decision block 210 whether or not the asset tag manager102 has been authorized to modify the electronic asset tag 108. Theasset tag manager 102 may determine its authorization status byreceiving an indication of its status from the asset device 106 overnetwork 104. If the asset tag manager 102 is not authorized to modifythe electronic asset tag 108, the method of flow chart 200 continues toelement 214. This prevents an unauthorized user or system fromimproperly modifying the electronic asset tag 108, helping to preservethe integrity of its contents. If the asset tag manager 102 isauthorized, the method of flow chart 200 continues to element 212,modifying the electronic asset tag 108. At element 212, the asset tagmanager 102 may modify or set any of the contents of the electronicasset tag 108, including the asset number. This allows an authorizeduser to modify, correct, or initially set up asset numbers for one ormore asset devices 106. The authorized user may accomplish themodifications remotely, providing an effective and efficient mechanismfor managing asset numbers and other contents of electronic asset tags108.

After modifying the electronic asset tag 108 (if such step wasperformed), the method of flow chart 200 continues to optional element214, recording an indication of the status of the electronic asset tag108, after which the flow chart terminates. In one embodiment, the assettag manager 102 may record any changes to the contents of a particularelectronic asset tag 108 discovered at element 204 or accomplished atelement 212.

FIG. 3 depicts an example of a flow chart for manually modifying theelectronic asset tag of an asset device according to one embodiment. Theelements of flow chart 300 may be performed, in one embodiment, by useror other operator in physical proximity to an asset device 106 with anelectronic access tag 108. Flow chart 300 begins with element 302,manually accessing an asset device 106. In one embodiment, the operatormay perform element 302 by utilizing a control panel or other user inputcomponent of the asset device 106. For example, an operator may use acontrol panel that allows users to configure the asset device 106,change various settings, view current settings or status, and the like.The operator, after manually accessing the asset device 106, may thenaccess the electronic asset tag 108 at element 304. At this element, theoperator may access the contents of the electronic asset tag 108 (suchas the asset number) via an output device of the asset device 106, suchas a control panel, monitor, printer, or audio device. The operator maytypically access any of the contents of the electronic asset tag 108without providing a password or other authentication.

In one example, the operator may type commands on a keypad that resultin the asset device 106 displaying contents of the electronic asset tag108 such as the asset number or contact information for the owner of theasset device 106. This aspect of the method of flow chart 300 replicatesthe basic functionality of someone walking up to an asset device 106 andreading a sticker attached to the asset device 106, but may provideadditional benefits. For example, the electronic asset tag 108 maycontain more information than a physical sticker, such as contactinformation for the outsourcing organization that owns the asset device106. The electronic asset 108 may also be more accurate and up to datethan a physical sticker.

The method of flow chart 300 continues to decision block 306, where theoperator may determine whether she should set or otherwise modify thecontents of the electronic asset tag 108. If the operator desires toattempt to modify the contents of the electronic asset tag 108, flowchart 300 continues to element 308; otherwise, flow chart 300terminates. At element 308, the operator may provide electronic assettag authorization to the asset device 106. The operator may provideauthorization in any fashion, such as a password, computer systemidentification, digital signature, digital authentication, or the like.In one example, the operator may enter an authorization password on auser input device (e.g., keypad) of the asset device 106. If theoperator is authorized (e.g., enters the correct password), the methodof flow chart 300 continues to element 312, and if the operator is notauthorized, the method of flow chart 300 terminates. At element 312, theoperator may modify or set any of the contents of the electronic assettag 108, including the asset number, after which the method terminates.This allows an authorized operator to modify, correct, or initially setup asset numbers for one or more asset devices 106. The method of flowchart 300 may work in conjunction with flow chart 200 of FIG. 2,allowing the contents of the electronic asset tag 108 to be modifiedboth by a central asset tag manager 102 as well as operators in thefield.

FIG. 4 depicts an example of a flow chart for modifying the electronicasset tag of an asset device in response to an authorized requestaccording to one embodiment. The elements of flow chart 400 may beperformed, in one embodiment, by components or combinations ofcomponents of an asset device 106. Flow chart 400 begins with optionalelement 402, connecting with an asset tag manager 102. In oneembodiment, the asset device 106 may establish a network connection suchas an SNMP connection over network 104 with the asset tag manager 102.Element 402 may be skipped if an operator is physically accessing theasset device 106, as a network connection need not be established. Afterthe connection is established (if element 402 is performed), the methodof flow chart 400 continues to optional element 404, where the assetdevice 106 may receive a request for some or all of the contents of theelectronic asset tag 108. The asset device 106 may receive the requestvia user input or from the asset tag manager 102 via network 104. If theasset device 106 does receive a request for the electronic asset tag 108contents, it may then provide the requested contents at element 406. Inone embodiment, the asset device 106 does not require authorization fordisplaying the contents of the electronic asset tag 108.

After providing the contents of the electronic asset tag 108 (ifrequested), the method of flow chart 400 continues to decision block408, where the asset device 106 may determine whether the asset tagmanager 102 and/or operator is authorized to modify the contents of theelectronic asset tag 108. Decision block 408 may be performed inresponse to a request to modify the electronic asset tag 108 from theasset tag manager 102 and/or operator. The asset device 106 may use anymethodology to determine whether the asset tag manager 102 and/oroperator is authorized, such as by comparing a supplied password to astored one, based on the identity of the computer system serving as theasset tag manager 102, based on a digital signature or authentication,or the like.

If the asset tag manager 102 and/or operator are authorized, the methodof flow chart 400 continues to element 410, receiving an indication ofthe modification to the electronic asset tag 410. Alternatively, thereceipt of such indication may also serve as the notice to the assetdevice 106 that a modification to the electronic asset tag 108 isdesired, resulting in element 410 being performed before element 408.The indication of the modification may include a new or modified assetnumber, outsourcer or customer information, or any other type ofinformation. After receiving the indication of a modification at element410, the asset device 106 may save the indication of the modification tothe electronic asset tag 108 at element 412, after which the methodterminates. The asset device 106 may save the modification to theelectronic asset tag 108 by saving changes to any of the electronicasset tag 108 content, saving a reset or changed asset number byreplacing the previous asset number, or saving any other indications.

If the asset tag manager 102 and/or operator are not authorized, theasset device 106 may optionally provide notice of the lack ofauthorization to the requester at element 414, after which the methodterminates. In one embodiment, the asset device 106 may provide therequester with additional opportunities to become authorized, such as byallowing the requester to attempt another password or provide adifferent identification.

FIG. 5 depicts an example of a flow chart for backing up and restoringthe electronic asset tag of an asset device according to one embodiment.The elements of flow chart 500 may be performed, in one embodiment, bycomponents or combinations of components of the asset management system100. Flow chart 500 begins with element 502, initializing a connectionwith an asset device 106. In one embodiment, the asset tag manager 102may perform element 502 by establishing a network connection overnetwork 104 with an asset device 106, such as an SNMP connection. Afterinitializing the connection with the asset device 106, the asset tagmanager 102 may access the contents of the electronic asset tag 108 atelement 504. A user of the asset tag manager 102 may, for example,access the asset number associated with an asset device 106 formonitoring or tracking purposes. The method of flow chart 500 continuesto element 506, recording the contents of the electronic asset tag 108to a separate device. At element 506, an asset tag manager 102 may savethe contents of the electronic asset tag 108 to a database 112 or otherstorage device.

At optional element 508, an operator may replace hardware and/orsoftware on the asset device 106 that contain some or all of thecontents of the electronic asset tag 106, such as in the event offailure of that hardware and/or software. In this embodiment, anoperator in physical proximity to the asset device 106 may performelements 502, 504, 506, and 508. The operator may access the assetdevice 106 via a keypad or other user interface and may record thecontents of the electronic asset device 108 to a separate device such asa memory key, floppy disk, or other backup device 110. This embodimentmay be useful in a scenario where someone servicing the asset device 106desires the capability to backup the contents, replace the hardwareand/or software, and then reload the contents of the electronic assettag. This methodology provides an additional level of permanence to theasset number and other contents of the electronic asset tag 108.

After completing the backup process at elements 502, 504, and 506, therestore process may then commence. At optional element 510, the assettag manager 106 and/or operator may provide authorization to modify theelectronic asset tag 108 contents, if such authorization is required.The asset tag manager 106 and/or operator may then reload the contentsto the electronic asset tag 108 at element 512, after which the methodterminates. The method of flow chart 500 may thus be used to backup andrestore the contents of the electronic asset tag 108, providing anadditional layer of security that may work in conjunction with storageof asset numbers and other content in database 112 as well as storage ofthe electronic asset tag 108 in multiple places in the asset device 106.

Each software program described herein may be operated on any type ofcomputer, such as personal computer, server, etc. Any programs may becontained on a variety of signal-bearing media. Illustrativesignal-bearing media include, but are not limited to: (i) informationpermanently stored on non-writable storage media (e.g., read-only memorydevices within a computer such as CD-ROM disks readable by a CD-ROMdrive); (ii) alterable information stored on writable storage media(e.g., floppy disks within a diskette drive or hard-disk drive); and(iii) information conveyed to a computer by a communications medium,such as through a computer or telephone network, including wirelesscommunications. The latter embodiment specifically includes informationdownloaded from the Internet, intranet or other networks. Suchsignal-bearing media, when carrying computer-readable instructions thatdirect the functions of the present invention, represent embodiments ofthe present invention.

In general, the routines executed to implement the embodiments of theinvention, may be part of an operating system or a specific application,component, program, module, object, or sequence of instructions. Thecomputer program of the present invention typically is comprised of amultitude of instructions that will be translated by the native computerinto a machine-readable format and hence executable instructions. Also,programs are comprised of variables and data structures that eitherreside locally to the program or are found in memory or on storagedevices. In addition, various programs described hereinafter may beidentified based upon the application for which they are implemented ina specific embodiment of the invention. However, it should beappreciated that any particular program nomenclature that follows isused merely for convenience, and thus the invention should not belimited to use solely in any specific application identified and/orimplied by such nomenclature.

It will be apparent to those skilled in the art having the benefit ofthis disclosure that the present invention contemplates methods,systems, and media for managing electronic asset tags for asset devices.It is understood that the form of the invention shown and described inthe detailed description and the drawings are to be taken merely asexamples. It is intended that the following claims be interpretedbroadly to embrace all the variations of the example embodimentsdisclosed.

1. A machine-accessible medium containing instructions effective, when executing in a data processing system, to cause said data processing system to perform operations comprising: accessing an electronic asset tag of an asset device, the electronic asset tag having contents comprising an asset number; providing electronic asset tag authorization to the asset device, wherein providing electronic asset tag authorization comprises providing a password, a digital signature, a digital authentication, and an indication of identification; and after providing electronic asset tag authorization, modifying the contents of the electronic asset tag of the asset device, the operations further comprising: (i) initializing a connection with the asset device, prior to accessing the electronic asset tag; (ii) recording the assessed electronic asset tag to a separate device; (iii) replacing hardware in the asset device, subsequent to the recording of the assessed electronic asset tag to the separate device, wherein the replaced hardware includes at least some contents of the electronic asset tag; (iv) providing authorization to modify the electronic asset tag, subsequent to replacing the hardware in the asset device; and (v) reloading the electronic asset tag from the separate device.
 2. The machine-accessible medium of claim 1, further comprising after modifying the electronic asset tag, recording an indication of a status for the electronic asset tag.
 3. The machine-accessible medium of claim 1, wherein the electronic asset tag comprises one or more of an indication of an owner associated with the asset device, and an indication of a customer associated with the asset device.
 4. The machine-accessible medium of claim 1, wherein modifying the contents of the electronic asset tag of the asset device comprises updating the asset number of the asset device.
 5. A system for managing asset numbers, the system comprising: one or more asset devices in communication with a network, the asset devices each having an electronic asset tag, the electronic asset tags having contents comprising an asset number associated with the asset device having the electronic asset tag, wherein electronic asset tag authorization is provided to the one or more asset devices, and wherein providing electronic asset tag authorization comprises providing a password, a digital signature, a digital authentication, and an indication of identification; and an asset tag manager in communication with the network, the asset tag manager being adapted to access the contents of the electronic asset tags of the one or more asset devices wherein a connection is initialized with a first asset device, prior to accessing a first electronic asset tag of the first asset device, wherein (i) the assessed first electronic asset tag is recorded to a separate device; (ii) hardware is replaced in the first asset device, subsequent to the recording of the assessed first electronic asset tag to the separate device; (iii) the replaced hardware includes at least some contents of the first electronic asset tag; (iv) authorization is provided to modify the first electronic asset tag, subsequent to replacing the hardware in the first asset device; and (v) the first electronic asset tag is reloaded to the first asset device from the separate device.
 6. The system of claim 5, further comprising a database in communication with the asset tag manager, the database being adapted to store contents of the electronic asset tags.
 7. The system of claim 5, wherein one or more of the asset devices are adapted to store the contents of their electronic asset tags in multiple locations within the asset device.
 8. The system of claim 5, wherein one or more of the asset devices are adapted to transmit the contents of their electronic asset tags to a backup device.
 9. The system of claim 5, wherein the asset tag manager is further adapted to modify the contents of the electronic asset tags of the one or more asset devices.
 10. The system of claim 5, wherein the asset tag manager is further adapted to reload to an asset device the contents of the electronic asset tag of the asset device. 